Multi-dimensional event engine for use in cloud environment with highly available network topology

ABSTRACT

Systems and methods including one or more processing modules and one or more non-transitory storage modules storing computing instructions configured to run on the one or more processing modules and perform acts of: initiating a cluster of controller instances in a cloud environment for executing a multi-dimensional event engine; and configuring the cluster of controller instances in a topology that provides availability and redundancy for the multi-dimensional event engine. An active controller instance is configured to: detect a current level of network traffic; receive the messages from an order management system; select a transmission rate for sending the messages to the fulfillment centers based on the current level of the network traffic; transmit the messages to the one or more fulfillment centers in accordance with the transmission rate; and dynamically adjust the transmission rate in response to detecting changes in the network traffic.

TECHNICAL FIELD

This disclosure relates generally to multi-dimensional event enginesthat are configured to auto-adjust transmission rates of message eventsthat are communicated to fulfillment centers, and that are incorporatedinto highly available and redundant network topologies to ensurecontinuous operations and to minimize system downtime.

BACKGROUND

The logistics of managing multiple fulfillment centers can be verycomplex. A single fulfillment center can be expected to process,package, and prepare massive volumes of orders each day (e.g., thousandsof orders each day). In addition to receiving and processing newlyreceived orders, the fulfillment center must account for ordercancellations and prioritized shipping requirements (e.g., for ordersthat must be delivered within short time periods). The fulfillmentcenter also must carefully manage inventory levels to ensure that thereceived orders are able to be fulfilled.

The manner in which conventional systems relay event information (e.g.,events related to new orders, cancellations and inventory updates) tofulfillment centers is inefficient and does not account for varyingvolumes of requests during peak and non-peak hours. Moreover, theseconventional systems fail to provide proper redundancies to ensure thatthe system does not experience downtime. If the systems becomesunavailable or crashes, it can cause shipping delays, inaccuracies ininventory tracking, and/or a variety of delivery problems (e.g., losingtrack of packages).

BRIEF DESCRIPTION OF THE DRAWINGS

To facilitate further description of the embodiments, the followingdrawings are provided in which:

FIG. 1 illustrates a front elevational view of a computer system that issuitable for implementing various embodiments of the systems disclosedin FIGS. 3 and 6;

FIG. 2 illustrates a representative block diagram of an example of theelements included in the circuit boards inside a chassis of the computersystem of FIG. 1;

FIG. 3 illustrates a representative block diagram of a system accordingto certain embodiments;

FIG. 4 is a sequence diagram illustrating a process flow forauto-adjusting transmission rates according to certain embodiments;

FIG. 5 is a flowchart for a method according to certain embodiments; and

FIG. 6 illustrates a representative block diagram of a portion of thesystem of FIG. 3 according to certain embodiments.

For simplicity and clarity of illustration, the drawing figuresillustrate the general manner of construction, and descriptions anddetails of well-known features and techniques may be omitted to avoidunnecessarily obscuring the present disclosure. Additionally, elementsin the drawing figures are not necessarily drawn to scale. For example,the dimensions of some of the elements in the figures may be exaggeratedrelative to other elements to help improve understanding of embodimentsof the present disclosure. The same reference numerals in differentfigures denote the same elements.

The terms “first,” “second,” “third,” “fourth,” and the like in thedescription and in the claims, if any, are used for distinguishingbetween similar elements and not necessarily for describing a particularsequential or chronological order. It is to be understood that the termsso used are interchangeable under appropriate circumstances such thatthe embodiments described herein are, for example, capable of operationin sequences other than those illustrated or otherwise described herein.Furthermore, the terms “include,” and “have,” and any variationsthereof, are intended to cover a non-exclusive inclusion, such that aprocess, method, system, article, device, or apparatus that comprises alist of elements is not necessarily limited to those elements, but mayinclude other elements not expressly listed or inherent to such process,method, system, article, device, or apparatus.

The terms “left,” “right,” “front,” “back,” “top,” “bottom,” “over,”“under,” and the like in the description and in the claims, if any, areused for descriptive purposes and not necessarily for describingpermanent relative positions. It is to be understood that the terms soused are interchangeable under appropriate circumstances such that theembodiments of the apparatus, methods, and/or articles of manufacturedescribed herein are, for example, capable of operation in otherorientations than those illustrated or otherwise described herein.

The terms “couple,” “coupled,” “couples,” “coupling,” and the likeshould be broadly understood and refer to connecting two or moreelements mechanically and/or otherwise. Two or more electrical elementsmay be electrically coupled together, but not be mechanically orotherwise coupled together. Coupling may be for any length of time,e.g., permanent or semi-permanent or only for an instant. “Electricalcoupling” and the like should be broadly understood and includeelectrical coupling of all types. The absence of the word “removably,”“removable,” and the like near the word “coupled,” and the like does notmean that the coupling, etc. in question is or is not removable.

As defined herein, two or more elements are “integral” if they arecomprised of the same piece of material. As defined herein, two or moreelements are “non-integral” if each is comprised of a different piece ofmaterial.

As defined herein, “real-time” can, in some embodiments, be defined withrespect to operations carried out as soon as practically possible uponoccurrence of a triggering event. A triggering event can include receiptof data necessary to execute a task or to otherwise process information.Because of delays inherent in transmission and/or in computing speeds,the term “real time” encompasses operations that occur in “near” realtime or somewhat delayed from a triggering event. In a number ofembodiments, “real time” can mean real time less a time delay forprocessing (e.g., determining) and/or transmitting data. The particulartime delay can vary depending on the type and/or amount of the data, theprocessing speeds of the hardware, the transmission capability of thecommunication hardware, the transmission distance, etc. However, in manyembodiments, the time delay can be less than approximately one second,two seconds, five seconds, or ten seconds.

As defined herein, “approximately” can, in some embodiments, mean withinplus or minus ten percent of the stated value. In other embodiments,“approximately” can mean within plus or minus five percent of the statedvalue. In further embodiments, “approximately” can mean within plus orminus three percent of the stated value. In yet other embodiments,“approximately” can mean within plus or minus one percent of the statedvalue.

DESCRIPTION OF EXAMPLES OF EMBODIMENTS

Embodiments of this disclosure relate to multi-dimensional event enginesthat are configured to auto-adjust transmission rates of message eventsthat are communicated to one or more fulfillment centers. Themulti-dimensional event engines can be incorporated into highlyavailable and redundant network topologies to ensure continuousoperations and minimize system downtime. The multi-dimensional eventengine can be accessible via a cloud environment that utilizes adistributed locking mechanism to allocate control among instances of themulti-dimensional event engine. An active instance of themulti-dimensional event engine can be configured to detect a currentlevel of network traffic, and to select a transmission rate for sendingthe message events to the one or more fulfillment centers based on thedetected level of network traffic. The transmission rate can bedynamically adjusted in response to detecting changes in the networktraffic, and additional message events can be sent using the dynamicallyadjusted transmission rate.

Turning to the drawings, FIG. 1 illustrates an exemplary embodiment of acomputer system 100, all of which or a portion of which can be suitablefor (i) implementing part or all of one or more embodiments of thetechniques, methods, and systems and/or (ii) implementing and/oroperating part or all of one or more embodiments of the memory storagemodules described herein. As an example, a different or separate one ofa chassis 102 (and its internal components) can be suitable forimplementing part or all of one or more embodiments of the techniques,methods, and/or systems described herein. Furthermore, one or moreelements of computer system 100 (e.g., a monitor 106, a keyboard 104,and/or a mouse 110, etc.) also can be appropriate for implementing partor all of one or more embodiments of the techniques, methods, and/orsystems described herein. Computer system 100 can comprise chassis 102containing one or more circuit boards (not shown), a Universal SerialBus (USB) port 112, a Compact Disc Read-Only Memory (CD-ROM) and/orDigital Video Disc (DVD) drive 116, and a hard drive 114. Arepresentative block diagram of the elements included on the circuitboards inside chassis 102 is shown in FIG. 2. A central processing unit(CPU) 210 in FIG. 2 is coupled to a system bus 214 in FIG. 2. In variousembodiments, the architecture of CPU 210 can be compliant with any of avariety of commercially distributed architecture families.

Continuing with FIG. 2, system bus 214 also is coupled to a memorystorage unit 208, where memory storage unit 208 can comprise (i)non-volatile memory, such as, for example, read only memory (ROM) and/or(ii) volatile memory, such as, for example, random access memory (RAM).The non-volatile memory can be removable and/or non-removablenon-volatile memory. Meanwhile, RAM can include dynamic RAM (DRAM),static RAM (SRAM), etc. Further, ROM can include mask-programmed ROM,programmable ROM (PROM), one-time programmable ROM (OTP), erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable ROM (EEPROM) (e.g., electrically alterable ROM (EAROM)and/or flash memory), etc. In these or other embodiments, memory storageunit 208 can comprise (i) non-transitory memory and/or (ii) transitorymemory.

In various examples, portions of the memory storage module(s) of thevarious embodiments disclosed herein (e.g., portions of the non-volatilememory storage module(s)) can be encoded with a boot code sequencesuitable for restoring computer system 100 (FIG. 1) to a functionalstate after a system reset. In addition, portions of the memory storagemodule(s) of the various embodiments disclosed herein (e.g., portions ofthe non-volatile memory storage module(s)) can comprise microcode suchas a Basic Input-Output System (BIOS) operable with computer system 100(FIG. 1). In the same or different examples, portions of the memorystorage module(s) of the various embodiments disclosed herein (e.g.,portions of the non-volatile memory storage module(s)) can comprise anoperating system, which can be a software program that manages thehardware and software resources of a computer and/or a computer network.The BIOS can initialize and test components of computer system 100(FIG. 1) and load the operating system. Meanwhile, the operating systemcan perform basic tasks such as, for example, controlling and allocatingmemory, prioritizing the processing of instructions, controlling inputand output devices, facilitating networking, and managing files.Exemplary operating systems can comprise one of the following: (i)Microsoft® Windows® operating system (OS) by Microsoft Corp. of Redmond,Wash., United States of America, (ii) Mac® OS X by Apple Inc. ofCupertino, Calif., United States of America, (iii) UNIX® OS, and (iv)Linux® OS. Further exemplary operating systems can comprise one of thefollowing: (i) the iOS® operating system by Apple Inc. of Cupertino,Calif., United States of America, (ii) the Blackberry® operating systemby Research In Motion (RIM) of Waterloo, Ontario, Canada, (iii) theWebOS operating system by LG Electronics of Seoul, South Korea, (iv) theAndroid™ operating system developed by Google, of Mountain View, Calif.,United States of America, (v) the Windows Mobile™ operating system byMicrosoft Corp. of Redmond, Wash., United States of America, or (vi) theSymbian™ operating system by Accenture PLC of Dublin, Ireland.

As used herein, “processor” and/or “processing module” means any type ofcomputational circuit, such as but not limited to a microprocessor, amicrocontroller, a controller, a complex instruction set computing(CISC) microprocessor, a reduced instruction set computing (RISC)microprocessor, a very long instruction word (VLIW) microprocessor, agraphics processor, a digital signal processor, or any other type ofprocessor or processing circuit capable of performing the desiredfunctions. In some examples, the one or more processing modules of thevarious embodiments disclosed herein can comprise CPU 210.

Alternatively, or in addition to, the systems and procedures describedherein can be implemented in hardware, or a combination of hardware,software, and/or firmware. For example, one or more application specificintegrated circuits (ASICs) can be programmed to carry out one or moreof the systems and procedures described herein. For example, one or moreof the programs and/or executable program components described hereincan be implemented in one or more ASICs. In many embodiments, anapplication specific integrated circuit (ASIC) can comprise one or moreprocessors or microprocessors and/or memory blocks or memory storage.

In the depicted embodiment of FIG. 2, various I/O devices such as a diskcontroller 204, a graphics adapter 224, a video controller 202, akeyboard adapter 226, a mouse adapter 206, a network adapter 220, andother I/O devices 222 can be coupled to system bus 214. Keyboard adapter226 and mouse adapter 206 are coupled to keyboard 104 (FIGS. 1-2) andmouse 110 (FIGS. 1-2), respectively, of computer system 100 (FIG. 1).While graphics adapter 224 and video controller 202 are indicated asdistinct units in FIG. 2, video controller 202 can be integrated intographics adapter 224, or vice versa in other embodiments. Videocontroller 202 is suitable for monitor 106 (FIGS. 1-2) to display imageson a screen 108 (FIG. 1) of computer system 100 (FIG. 1). Diskcontroller 204 can control hard drive 114 (FIGS. 1-2), USB port 112(FIGS. 1-2), and CD-ROM drive 116 (FIGS. 1-2). In other embodiments,distinct units can be used to control each of these devices separately.

Network adapter 220 can be suitable to connect computer system 100(FIG. 1) to a computer network by wired communication (e.g., a wirednetwork adapter) and/or wireless communication (e.g., a wireless networkadapter). In some embodiments, network adapter 220 can be plugged orcoupled to an expansion port (not shown) in computer system 100 (FIG.1). In other embodiments, network adapter 220 can be built into computersystem 100 (FIG. 1). For example, network adapter 220 can be built intocomputer system 100 (FIG. 1) by being integrated into the motherboardchipset (not shown), or implemented via one or more dedicatedcommunication chips (not shown), connected through a PCI (peripheralcomponent interconnector) or a PCI express bus of computer system 100(FIG. 1) or USB port 112 (FIG. 1).

Returning now to FIG. 1, although many other components of computersystem 100 are not shown, such components and their interconnection arewell known to those of ordinary skill in the art. Accordingly, furtherdetails concerning the construction and composition of computer system100 and the circuit boards inside chassis 102 are not discussed herein.

Meanwhile, when computer system 100 is running, program instructions(e.g., computer instructions) stored on one or more of the memorystorage module(s) of the various embodiments disclosed herein can beexecuted by CPU 210 (FIG. 2). At least a portion of the programinstructions, stored on these devices, can be suitable for carrying outat least part of the techniques and methods described herein.

Further, although computer system 100 is illustrated as a desktopcomputer in FIG. 1, there can be examples where computer system 100 maytake a different form factor while still having functional elementssimilar to those described for computer system 100. In some embodiments,computer system 100 may comprise a single computer, a single server, ora cluster or collection of computers or servers, or a cloud of computersor servers. Typically, a cluster or collection of servers can be usedwhen the demand on computer system 100 exceeds the reasonable capabilityof a single server or computer. In certain embodiments, computer system100 may comprise a portable computer, such as a laptop computer. Incertain other embodiments, computer system 100 may comprise a mobileelectronic device, such as a smartphone. In certain additionalembodiments, computer system 100 may comprise an embedded system.

Turning ahead in the drawings, FIG. 3 illustrates a block diagram of asystem 300 that can be employed for efficiently processing andtransmitting message events to fulfillment centers and ensuring systemavailability as described in greater detail below. System 300 is merelyexemplary and embodiments of the system are not limited to theembodiments presented herein. System 300 can be employed in manydifferent embodiments or examples not specifically depicted or describedherein. In some embodiments, certain elements or modules of system 300can perform various procedures, processes, and/or activities. In theseor other embodiments, the procedures, processes, and/or activities canbe performed by other suitable elements or modules of system 300.

Generally, therefore, system 300 can be implemented with hardware and/orsoftware, as described herein. In some embodiments, part or all of thehardware and/or software can be conventional, while in these or otherembodiments, part or all of the hardware and/or software can becustomized (e.g., optimized) for implementing part or all of thefunctionality of system 300 described herein.

In some embodiments, system 300 can include a cloud environment 310, aweb server 320, a multi-dimensional event engine 330 and an ordermanagement system 370. The system 300 may also include a fulfillmentcenter 390 and a fulfillment system 395 in certain embodiments. Thecloud environment 310, the web server 320, the multi-dimensional eventengine 330, the order management system 370, fulfillment center 390, andthe fulfillment system 395 can each be a computer system, such ascomputer system 100 (FIG. 1), as described above, and can each be asingle computer, a single server, or a cluster or collection ofcomputers or servers, or a cloud of computers or servers. In anotherembodiment, a single computer system can host each of two or more cloudenvironment 310, the web server 320, the multi-dimensional event engine330, the order management system 370, fulfillment center 390, and thefulfillment system 395 are described herein.

In many embodiments, system 300 also can comprise user computers 340. Insome embodiments, user computers 340 can be mobile devices. A mobileelectronic device can refer to a portable electronic device (e.g., anelectronic device easily conveyable by hand by a person of average size)with the capability to present audio and/or visual data (e.g., text,images, videos, music, etc.). For example, a mobile electronic devicecan comprise at least one of a digital media player, a cellulartelephone (e.g., a smartphone), a personal digital assistant, a handhelddigital computer device (e.g., a tablet personal computer device), alaptop computer device (e.g., a notebook computer device, a netbookcomputer device), a wearable user computer device, or another portablecomputer device with the capability to present audio and/or visual data(e.g., images, videos, music, etc.). Thus, in many examples, a mobileelectronic device can comprise a volume and/or weight sufficiently smallas to permit the mobile electronic device to be easily conveyable byhand. For examples, in some embodiments, a mobile electronic device canoccupy a volume of less than or equal to approximately 1790 cubiccentimeters, 2434 cubic centimeters, 2876 cubic centimeters, 4056 cubiccentimeters, and/or 5752 cubic centimeters. Further, in theseembodiments, a mobile electronic device can weigh less than or equal to15.6 Newtons, 17.8 Newtons, 22.3 Newtons, 31.2 Newtons, and/or 44.5Newtons.

Exemplary mobile electronic devices can comprise (i) an iPod®, iPhone®,iTouch®, iPad®, MacBook® or similar product by Apple Inc. of Cupertino,Calif., United States of America, (ii) a Blackberry® or similar productby Research in Motion (RIM) of Waterloo, Ontario, Canada, (iii) a Lumia®or similar product by the Nokia Corporation of Keilaniemi, Espoo,Finland, and/or (iv) a Galaxy™ or similar product by the Samsung Groupof Samsung Town, Seoul, South Korea. Further, in the same or differentembodiments, a mobile electronic device can comprise an electronicdevice configured to implement one or more of (i) the iPhone® operatingsystem by Apple Inc. of Cupertino, Calif., United States of America,(ii) the Blackberry® operating system by Research In Motion (RIM) ofWaterloo, Ontario, Canada, (iii) the Palm® operating system by Palm,Inc. of Sunnyvale, Calif., United States, (iv) the Android™ operatingsystem developed by the Open Handset Alliance, (v) the Windows Mobile™operating system by Microsoft Corp. of Redmond, Wash., United States ofAmerica, or (vi) the Symbian™ operating system by Nokia Corp. ofKeilaniemi, Espoo, Finland.

Further still, the term “wearable user computer device” as used hereincan refer to an electronic device with the capability to present audioand/or visual data (e.g., text, images, videos, music, etc.) that isconfigured to be worn by a user and/or mountable (e.g., fixed) on theuser of the wearable user computer device (e.g., sometimes under or overclothing; and/or sometimes integrated with and/or as clothing and/oranother accessory, such as, for example, a hat, eyeglasses, a wristwatch, shoes, etc.). In many examples, a wearable user computer devicecan comprise a mobile electronic device, and vice versa. However, awearable user computer device does not necessarily comprise a mobileelectronic device, and vice versa.

In specific examples, a wearable user computer device can comprise ahead mountable wearable user computer device (e.g., one or more headmountable displays, one or more eyeglasses, one or more contact lenses,one or more retinal displays, etc.) or a limb mountable wearable usercomputer device (e.g., a smart watch). In these examples, a headmountable wearable user computer device can be mountable in closeproximity to one or both eyes of a user of the head mountable wearableuser computer device and/or vectored in alignment with a field of viewof the user.

In more specific examples, a head mountable wearable user computerdevice can comprise (i) Google Glass™ product or a similar product byGoogle Inc. of Menlo Park, Calif., United States of America; (ii) theEye Tap™ product, the Laser Eye Tap™ product, or a similar product byePI Lab of Toronto, Ontario, Canada, and/or (iii) the Raptyr™ product,the STAR 1200™ product, the Vuzix Smart Glasses M100™ product, or asimilar product by Vuzix Corporation of Rochester, N.Y., United Statesof America. In other specific examples, a head mountable wearable usercomputer device can comprise the Virtual Retinal Display™ product, orsimilar product by the University of Washington of Seattle, Wash.,United States of America. Meanwhile, in further specific examples, alimb mountable wearable user computer device can comprise the iWatch™product, or similar product by Apple Inc. of Cupertino, Calif., UnitedStates of America, the Galaxy Gear or similar product of Samsung Groupof Samsung Town, Seoul, South Korea, the Moto 360 product or similarproduct of Motorola of Schaumburg, Ill., United States of America,and/or the Zip™ product, One™ product, Flex™ product, Charge™ product,Surge™ product, or similar product by Fitbit Inc. of San Francisco,Calif., United States of America.

In some embodiments, web server 320 can be in data communication througha network 380 (e.g., the Internet) with user computers (e.g., 340). Incertain embodiments, user computers 340 can be desktop computers, laptopcomputers, smart phones, tablet devices, and/or other endpoint devices.Web server 320 can host one or more websites. For example, web server320 can host an online shopping website that allows users to browseand/or search for products, to add products to an electronic shoppingcart, and/or to purchase products, in addition to other suitableactivities.

In many embodiments, the cloud environment 310, the web server 320, themulti-dimensional event engine 330, the order management system 370, thefulfillment center 390, and the fulfillment system 395 can each compriseone or more input devices (e.g., one or more keyboards, one or morekeypads, one or more pointing devices such as a computer mouse orcomputer mice, one or more touchscreen displays, a microphone, etc.),and/or can each comprise one or more display devices (e.g., one or moremonitors, one or more touch screen displays, projectors, etc.). In theseor other embodiments, one or more of the input device(s) can be similaror identical to keyboard 104 (FIG. 1) and/or a mouse 110 (FIG. 1).Further, one or more of the display device(s) can be similar oridentical to monitor 106 (FIG. 1) and/or screen 108 (FIG. 1). The inputdevice(s) and the display device(s) can be coupled to the processingmodule(s) and/or the memory storage module(s) for the cloud environment310, the web server 320, the multi-dimensional event engine 330, theorder management system 370, the fulfillment center 390, and thefulfillment system 395 in a wired manner and/or a wireless manner, andthe coupling can be direct and/or indirect, as well as locally and/orremotely. As an example of an indirect manner (which may or may not alsobe a remote manner), a keyboard-video-mouse (KVM) switch can be used tocouple the input device(s) and the display device(s) to the processingmodule(s) and/or the memory storage module(s). In some embodiments, theKVM switch also can be part of the cloud environment 310, the web server320, the multi-dimensional event engine 330, the order management system370, the fulfillment center 390, and/or the fulfillment system 395. In asimilar manner, the processing module(s) and the memory storagemodule(s) can be local and/or remote to each other.

In many embodiments, the cloud environment 310, the web server 320, themulti-dimensional event engine 330, the order management system 370, thefulfillment center 390, and the fulfillment system 395 can be configuredto communicate with one or more user computers 340. In some embodiments,user computers 340 also can be referred to as customer computers. Insome embodiments, the cloud environment 310, the web server 320, themulti-dimensional event engine 330, the order management system 370, thefulfillment center 390, and the fulfillment system 395 can communicateor interface (e.g., interact) with one or more customer computers (suchas user computers 340) through a network 380, e.g., such as one thatincludes the Internet. Network 380 can be an intranet that is not opento the public. Accordingly, in many embodiments, the cloud environment310, the web server 320, the multi-dimensional event engine 330, theorder management system 370, the fulfillment center 390, and/or thefulfillment system 395 (and/or the software used by such systems) canrefer to a back end of system 300 operated by an operator and/oradministrator of system 300, and user computers 340 (and/or the softwareused by such systems) can refer to a front end of system 300 used by oneor more users 305, respectively. In some embodiments, users 305 also canbe referred to as customers, in which case, user computers 340 can bereferred to as customer computers. In these or other embodiments, theoperator and/or administrator of system 300 can manage system 300, theprocessing module(s) of system 300, and/or the memory storage module(s)of system 300 using the input device(s) and/or display device(s) ofsystem 300.

Meanwhile, in many embodiments, the cloud environment 310, the webserver 320, the multi-dimensional event engine 330, the order managementsystem 370, the fulfillment center 390, and the fulfillment system 395also can be configured to communicate with one or more databases. Theone or more databases can comprise a product database that containsinformation about products, items, or SKUs (stock keeping units) sold bya retailer. The one or more databases can be stored on one or morememory storage modules (e.g., non-transitory memory storage module(s)),which can be similar or identical to the one or more memory storagemodule(s) (e.g., non-transitory memory storage module(s)) describedabove with respect to computer system 100 (FIG. 1). Also, in someembodiments, for any particular database of the one or more databases,that particular database can be stored on a single memory storage moduleof the memory storage module(s), and/or the non-transitory memorystorage module(s) storing the one or more databases or the contents ofthat particular database can be spread across multiple ones of thememory storage module(s) and/or non-transitory memory storage module(s)storing the one or more databases, depending on the size of theparticular database and/or the storage capacity of the memory storagemodule(s) and/or non-transitory memory storage module(s).

The one or more databases can each comprise a structured (e.g., indexed)collection of data and can be managed by any suitable databasemanagement systems configured to define, create, query, organize,update, and manage database(s). Exemplary database management systemscan include MySQL (Structured Query Language) Database, PostgreSQLDatabase, Microsoft SQL Server Database, Oracle Database, SAP (Systems,Applications, & Products) Database, and IBM DB2 Database.

Meanwhile, communication between the cloud environment 310, the webserver 320, the multi-dimensional event engine 330, the order managementsystem 370, the fulfillment center 390, and the fulfillment system 395,and/or the one or more databases can be implemented using any suitablemanner of wired and/or wireless communication. Accordingly, system 300can comprise any software and/or hardware components configured toimplement the wired and/or wireless communication. Further, the wiredand/or wireless communication can be implemented using any one or anycombination of wired and/or wireless communication network topologies(e.g., ring, line, tree, bus, mesh, star, daisy chain, hybrid, etc.)and/or protocols (e.g., personal area network (PAN) protocol(s), localarea network (LAN) protocol(s), wide area network (WAN) protocol(s),cellular network protocol(s), powerline network protocol(s), etc.).Exemplary PAN protocol(s) can comprise Bluetooth, Zigbee, WirelessUniversal Serial Bus (USB), Z-Wave, etc.; exemplary LAN and/or WANprotocol(s) can comprise Institute of Electrical and ElectronicEngineers (IEEE) 802.3 (also known as Ethernet), IEEE 802.11 (also knownas WiFi), etc.; and exemplary wireless cellular network protocol(s) cancomprise Global System for Mobile Communications (GSM), General PacketRadio Service (GPRS), Code Division Multiple Access (CDMA),Evolution-Data Optimized (EV-DO), Enhanced Data Rates for GSM Evolution(EDGE), Universal Mobile Telecommunications System (UMTS), DigitalEnhanced Cordless Telecommunications (DECT), Digital AMPS (IS-136/TimeDivision Multiple Access (TDMA)), Integrated Digital Enhanced Network(iDEN), Evolved High-Speed Packet Access (HSPA+), Long-Term Evolution(LTE), WiMAX, etc. The specific communication software and/or hardwareimplemented can depend on the network topologies and/or protocolsimplemented, and vice versa. In many embodiments, exemplarycommunication hardware can comprise wired communication hardwareincluding, for example, one or more data buses, such as, for example,universal serial bus(es), one or more networking cables, such as, forexample, coaxial cable(s), optical fiber cable(s), and/or twisted paircable(s), any other suitable data cable, etc. Further exemplarycommunication hardware can comprise wireless communication hardwareincluding, for example, one or more radio transceivers, one or moreinfrared transceivers, etc. Additional exemplary communication hardwarecan comprise one or more networking components (e.g.,modulator-demodulator components, gateway components, etc.).

A number of embodiments can include a system. The system can include oneor more processing modules and one or more non-transitory storagemodules storing computing instructions configured to run on the one ormore processing modules. The one or more storage modules can beconfigured to run on the one or more processing modules and perform theacts of: initiating a cluster of controller instances in a cloudenvironment for executing a multi-dimensional event engine that isconfigured to control routing of messages to one or more fulfillmentcenters; and configuring the cluster of controller instances in atopology that provides availability and redundancy for themulti-dimensional event engine. The topology applies a distributed lockto designate an active controller instance selected from the cluster ofcontroller instances to be utilized as the multi-dimensional eventengine. The active controller instance selected to be utilized as themulti-dimensional event engine is configured to: detect a current levelof network traffic; receive the messages from an order managementsystem; select a transmission rate for sending the messages to the oneor more fulfillment centers based on the current level of the networktraffic that is detected; transmit the messages to the one or morefulfillment centers in accordance with the transmission rate;dynamically adjust the transmission rate to create an adjustedtransmission rate in response to detecting changes in the networktraffic; and transmit additional ones of the messages to the one or morefulfillment centers in accordance with the adjusted transmission rate.

Various embodiments include a method. The method can include:initiating, with one or more processing modules, a cluster of controllerinstances in a cloud environment for executing a multi-dimensional eventengine that is configured to control routing of messages to one or morefulfillment centers; and configuring, with the one or more processingmodules, the cluster of controller instances in a topology that providesavailability and redundancy for the multi-dimensional event engine. Thetopology applies a distributed lock to designate an active controllerinstance selected from the cluster of controller instances to beutilized as the multi-dimensional event engine. The active controllerinstance selected to be utilized as the multi-dimensional event engineis configured to: detect a current level of network traffic; receive themessages from an order management system; select a transmission rate forsending the messages to the one or more fulfillment centers based on thecurrent level of the network traffic that is detected; transmit themessages to the one or more fulfillment centers in accordance with thetransmission rate; dynamically adjust the transmission rate to create anadjusted transmission rate in response to detecting changes in thenetwork traffic; and transmit additional ones of the messages to the oneor more fulfillment centers in accordance with the adjusted transmissionrate.

Conventional systems for managing fulfillment centers are insufficientfor many reasons. One major problem is that conventional systems fail toprovide proper redundancies to ensure that the system does not gooffline or become unavailable. A system failure can have catastrophicconsequences, which can result in shipping delays, inaccurate inventorytracking, and various delivery problems (e.g., losing track ofpackages). Another major problem is that the message transmissiontechniques utilized by conventional systems fail to relay eventinformation (e.g., pertaining to new orders, order cancellations, orderupdates, and inventory updates) to the fulfillment centers in aneffective manner. Typically, the conventional systems send messagespertaining to these events to the fulfillment centers at staticallydefined intervals (e.g., every half hour or so). The manner in which themessages are transmitted to the fulfillment centers does not account fornetwork traffic. Moreover, the message dispatching techniques treathigh-priority messages (e.g., messages for 2-day shipping and/ormessages that indicate shipments are not expected to be delivered ontime) in the same manner as all of the other messages. Transmitting themessages to the fulfillment centers in this manner can result in latedelivery of shipments to customers, especially at times when themessages are being transmitted to the fulfillment centers during peakhours and the fulfillment centers are receiving massive volumes oforders.

The principles described herein relate to a multi-dimensional eventengine that overcomes the aforementioned problems, as well as otherproblems not specifically mentioned. The multi-dimensional event enginecan be integrated into a cloud environment that utilizes anactive-standby network topology to provide redundancy and to ensure thatthe multi-dimensional event engine remains operational. In the eventthat the multi-dimensional event engine becomes unavailable (e.g.,because of a system failure, a hardware failure, and/or a softwarefailure), a separate instance of the multi-dimensional event engine canbe immediately activated to replace the failed instance. This can beaccomplished, at least in part, by enforcing a distributed lockmechanism that controls which instance of the multi-dimensional eventengine will be active. This configuration can ensure that themulti-dimensional event engine is highly available and that any downtimeis minimized to the extent possible.

The multi-dimensional event engine also can be configured to transmitinformation to the fulfillment centers utilizing messaging techniquesthat account for network traffic levels and high-priority messages. Morespecifically, the multi-dimensional event engine can monitor networktraffic levels and automatically adjust the transmission rate at whichmessages are sent to the fulfillment centers based on the current levelof network traffic. The transmission rate can be increased as networktraffic increases, and the transmission rate can be lowered as networktraffic decreases. Adjusting the transmission rate in this mannerpermits the fulfilment centers to process the messages more effectively,and to ensure orders are delivered on time. In addition, prioritizedmessages are processed with a specialized event handler that ensuresthese messages are given priority and processed immediately. In certainembodiments, the specialized event handler transmits the prioritizedmessages to the fulfillment centers via dedicated communication channelsto ensure expedited processing of these messages.

Referring back to FIG. 3, customers (e.g., users 305) can submitrequests via an order management system 370. The order management system370 can represent an electronic platform or system that is configured toprocess orders 372 (e.g., orders for delivering or shipping products).Customers can access the order management system 370 to place new orders372, cancel existing orders 372, update existing orders 372, and/orperform other related functions. The order management system 370 canreceive these requests via websites (e.g., an online shopping websitethat enables products to be purchased), via phone-based order systems,at physical store locations (e.g., where customers place orders withpersonnel at the store locations), and/or in other ways.

The order management system 370 generates messages 371 corresponding toeach of the requests made by the customers (e.g., the requests for neworders, cancellations, updates, and/or replacements). The ordermanagement system 370 (or other system component) also can be configuredto generate messages 371 associated with inventory information (e.g.,messages that provide information related to inventory updates, messagesthat identify current inventory levels, messages that includeinformation associated with scheduled inventory shipments, and/ormessages that include other types of inventory information).

The generated messages 371 are transmitted to a multi-dimensional eventengine 330 stored in a cloud environment 310. The messages 371 can betransmitted directly to the multi-dimensional event engine 330 and/orover the network 380. The multi-dimensional event engine 330 processesthe messages 371 and transmits the messages 371 (e.g., via the network380 and/or directly) to the appropriate fulfillment centers 390. Asdescribed in further detail below, the multi-dimensional event engine330 transmits the messages 371 to the fulfillment centers 390 utilizingmessaging techniques that account for varying network traffic levels,high-priority messages, and other factors. The messages 371 are receivedby fulfillment systems 395 located at the fulfillment centers 390.

The fulfillment centers 390 can represent any physical location (e.g.,warehouse, building, storefront, and/or other structure) that assistswith fulfilling orders, storing products, managing inventory, and/ordelivering the products to customers (e.g., users 305). The fulfillmentcenters 390 can each include a fulfillment system 395. The fulfillmentsystem 395 can include one or more computing devices (e.g., computersand/or servers) and/or software solutions that are configured to performfunctions that assist the fulfillment centers 390 with processingcustomer requests (e.g., requests for new orders, order cancellations,order updates, replacement orders, and/or other types of requests). Thefulfillment system 395 also can be configured to perform functionsassociated with managing, tracking, and updating inventory information.The fulfillment system 395 utilizes the messages 371 received from themulti-dimensional event engine 330 to facilitate performance of theseactivities. The messages 371 received from the multi-dimensional eventengine 330 can include messages 371 associated with placing new orders,cancelling existing orders, updating existing orders, and/or updatinginventory information.

The cloud environment 310 stores and executes a multi-dimensional eventengine 330 that receives messages 371 from the order management system370 (and/or other components), processes the messages, and transmits themessages to fulfillment centers 390. The cloud environment 310 cancomprise a plurality of shared servers and server resources that aremade available via the network 380. In certain embodiments, the cloudenvironment 310 can comprise a network of remote servers hosted on thenetwork 380 to store, manage, and process data as described herein. Inother embodiments, the cloud environment 310 can alternatively, oradditionally, comprise a network of local servers that store, manage,and process data as described herein. As described in further detailbelow, the cloud environment 310 can execute a multi-dimensional eventengine 330 that can be configured to automate processing capabilitiesfor facilitating supply chain flows that involve processing new orders,updating existing orders, processing order cancellations, tracking andupdating inventory levels, and/or performing other related activities.

The multi-dimensional event engine 330 can be implemented utilizing atopology 353 that ensures high availability and redundancy. For example,in certain embodiments, the multi-dimensional event engine 330 isimplemented in an “active-standby” network topology that includes aninstance cluster 350 comprising one or more active controller instances351 and one or more standby controller instances 352. In thisactive-standby topology, a plurality of instances is initiated for themulti-dimensional event engine 330 in the cloud environment 310 duringstartup. Each instance of the multi-dimensional event engine 330included in the instance cluster 350 tries to acquire a singledistributed lock. The multi-dimensional event engine 330 can include adistributed lock manager for determining which instance is assigned thedistributed lock. The instance that is assigned the distributed lock isdesignated as the active controller instance 351, and all of the otherinstances are designated as standby controller instances 352. The activecontroller instance 351 will serve as the multi-dimensional event engine330 and will process all of the messages 371 received by the ordermanagement system 370 and/or other components.

The standby controller instances 352 continuously poll the distributedlock manager for the availability of the distributed lock. In the eventthat the active controller instance 351 crashes or otherwise becomesunavailable (e.g., due to a cloud outage in a portion of the cloudenvironment 310), the distributed lock will be assigned to one of thestandby controller instances 352. The standby controller instance 352that is allocated the distributed lock will then become the activecontroller instance 351. If the previous active controller instance 351comes back online at some point, it will join the other standbycontroller instances 352 and continuously poll for availability of thedistributed lock. In this manner, the topology 353 utilized to implementthe multi-dimensional event engine 330 ensures high availability for theoverall system and provides additional layers of redundancy.

It should be recognized that other types of topologies 353 can beutilized in connection with the principles described in this disclosure.For example, an “active-active” topology an be utilized in some cases.Regardless of which topology 353 is used, the selected topology 353 ispreferably configured in a manner that ensures high availability of themulti-dimensional event engine 330 and other system components.

The manner in which the multi-dimensional event engine 330 transmitsmessages 371 to the fulfillment centers (e.g., to the fulfillment system395) is unique and can provide a variety of advantages. Themulti-dimensional event engine 330 controls delivery of the messages 371across a plurality of dimensions. For example, the multi-dimensionalevent engine 330 can control the transmission rate of messages 371(e.g., to change the rate during peak and off-peak hours), expediteprocessing of prioritized messages, and customize the transmission ofmessages according to various supply chain measures (e.g., byfulfillment center and/or by message type). To enable control over thesedimensions, the multi-dimensional event engine 330 stores dimensiondefinitions 335 that can be utilized to classify messages and to specifyhow routing of the messages 371 is accomplished. More specifically,metadata included in the messages 371 is compared to the dimensiondefinitions 335 and the multi-dimensional event engine 330 determineshow the messages 371 should be dispatched to the fulfillment centers 390based on this comparison.

In certain embodiments, a first set of base dimensions included in thedimension definitions 335 can be used to control the transmission rateof the messages 371. A second set of priority dimensions included in thedimension definitions 335 can be utilized to enable advanced flowcontrol for prioritized messages. A third set of supply chain dimensionsincluded in the dimension definitions 335 can be utilized to control theflow of messages 371 for certain types of supply chains and/or toaccount for certain logistical measures. Each of these is described infurther detail below.

In certain embodiments, the first set of base dimensions used to controlthe transmission rate of the messages 371 includes a time dimensionindicating a time period (e.g., 2 minutes or 30 minutes) and a batchsize dimension indicating a threshold number of messages 371. The timeperiod can be set to any time period (e.g., 1 second, 1 minute, 10minutes, 1 hour, 1 day, etc.), and the batch size dimension can be setto any positive integer value (e.g., 10, 100, 1,000, 5,000, etc.). Themulti-dimensional event engine 330 will transmit a batch of messages toone or more of the fulfillment centers 390 whenever the time periodexpires or whenever the threshold number of messages 371 is reached,whichever occurs first. Thus, adjusting the parameters associated withthe time dimension and the batch size dimension can be utilized toadjust the rate at which messages 371 are communicated to thefulfillment centers 390.

In certain embodiments, the multi-dimensional event engine 330 detectsthe current level of network traffic. The current level of networktraffic can be determined by monitoring the volume of messages 371 thatare being submitted via the order management system 370, monitoring thevolume of messages 371 that are being received by the multi-dimensionalevent engine 330, monitoring the number of users 305 accessing the ordermanagement system 370, and/or monitoring other similar metrics. Thetransmission rate of the multi-dimensional event engine 330 isautomatically adjusted based on the detected network traffic. In certainembodiments, the transmission rate can be increased in response todetecting increasing levels of network traffic, and can be decreased inresponse to detecting lower levels of network traffic. This dynamicadjustment of the transmission rates permits the fulfillment centers toprocess the messages 371 more effectively and to ensure that deliveriesare shipped on time, while accounting for varying volumes of messages371 during peak hours and off-peak hours. This represents an improvementupon conventional techniques, which typically send the messages 371 atstatic, pre-defined intervals, thus resulting in the occurrence ofbacklogs during peak hours.

The second set of priority dimensions, which can be utilized to provideadvanced flow control for prioritized messages, can utilize parametersthat indicate whether or not a message 371 is to be treated as aprioritized message. Messages 371 can be prioritized for a variety ofdifferent reasons. For example, the second set of priority dimensionscan include an expedited shipping dimension that indicates whether anorder 372 is subject to expedited shipping preferences (e.g., 2-dayshipping or same-day shipping). The second set of priority dimensionscan also include an anomaly dimension that indicates shipping exceptionshave been detected for an order (e.g., when the system 300 detects thatan order 372 will not be delivered within an expected timeframe or thatproducts have been damaged). The expedited shipping and anomalydimensions include parameters that indicate whether a message 371 shouldbe subject to prioritized treatment. If the metadata included in amessage 371 indicates that the message is a prioritized message (or suchis detected by the multi-dimensional event engine 330), the dimensiondefinitions 335 will identify these message 371 as one which requiresspecial treatment and the message 371 will be processed by a specializedhandler incorporated into the multi-dimensional event engine 330. Thespecialized handler can cause prioritized messages to be sent to thefulfillment centers 390 at higher transmission rates than other messagesthat are not prioritized. The specialized handler also can causeprioritized messages to be sent to the fulfillment system 395 of afulfillment center 390 via a separate, prioritized communicationchannel. This can involve sending the prioritized messages to computerdevices, inboxes, message queues, and/or individuals which are dedicatedto expedite processing of the messages at the fulfillment centers 390.

The third set of supply chain dimensions is utilized to customize andcontrol the flow of messages 371 for certain types of supply chainsand/or to account for certain logistical measures. The supply chaindimensions can include a message type dimension that includes aparameter that identifies the supply chain or process flow associatedwith the message 371. For example, the message type dimension canidentify whether a message 371 is associated with a supply chain orprocess flow for a new order, an order cancellation, an inventoryupdate, an order modification, an order replacement, and/or another typeof event. The supply chain dimensions also can include a facilityidentifier dimension that identifies which fulfillment center 390 shouldreceive the message 371 pertaining to an order 372 and/or fulfill theorder 372 associated with the message 371. The supply chain dimensionscan further include a facility type dimension that includes a parameterthat identifies a type of facility that is processing the order 372. Forexample, the facility type dimension can determine whether or not thefacility utilizes automated equipment to sort, package, and/or otherwisefacilitate the delivery of orders 372. The type of equipment availableat a fulfillment center 390 can affect whether or not a package is to berouted to the fulfillment center 390.

The third set of supply chain dimensions may be utilized to customizeand control the flow of messages 371 to the fulfillment centers 390. Forexample, these dimensions can be utilized to aggregate the messages fordifferent supply chains in different groupings for transmission, and/orto route the messages for different supply chains to appropriatechannels of the fulfillment system 395 for processing.

As mentioned above, the multi-dimensional event engine 330 storesdimension definitions 335 that are utilized to process the messages 371.The dimension definitions 335 can represent programming objects, codeinstructions, and/or scripts that are utilized to identify andcategorize the messages 371 and to route the messages to the fulfillmentcenters 390 based on the parameters specified in the dimensiondefinitions 335 (e.g., the parameters that define the transmissionrates, prioritized message handling, and customized supply chainhandling). Metadata included in the messages 371 is compared to thedimension definitions 335 to determine how messages 371 are to be routedto the fulfillment centers 390. Exemplary dimension definitions 335 aredescribed below to demonstrate how this is accomplished.

Example 1 (below) includes pseudocode for defining an exemplarydimension definition 335 that is utilized to identify and route messages371 associated with new orders 372.

EXAMPLE 1

{    ″duration″ : ″10 min″,    ″message_count″ : ″1000″,    ″process_type″ : ″OrderRequest″,    “partnerId” : “6559” }

The “process_type” parameter is set to “OrderRequest” to specify thatthis dimension definition 335 applies to messages 371 pertaining to neworders. The parameter can alternatively identify other types of supplychains or process flows (e.g., dealing with order cancellations orinventory updates). The first two parameters (i.e., “duration” and“message_count”) define base dimensions that control the transmissionrate of the messages that fall within the scope of this dimensiondefinition 335. For example, the parameters specify that a batch ofmessages will be transmitted to a fulfillment center 390 every 10minutes or upon receiving 1,000 messages for new orders, whicheveroccurs first. As mentioned above, these values can be adjusted based onpeak and non-peak levels to modify the transmission rate. The“partnerId” parameter identifies a specific fulfillment center 390associated with fulfilling the new orders (e.g., a specific fulfilmentcenter 390 that is designated to process and fulfill the order).

When messages 371 are received by the multi-dimensional event engine330, metadata included in the messages 371 will be compared to aplurality of dimension definitions 335, such as the example providedabove, to determine how the messages 371 should be dispatched. If themetadata of a message 371 matches the parameters for a dimensiondefinition 335 (e.g., matches the “process_type” and “partnerId”parameters), then the message 371 will be routed in accordance with theparameters of the dimension definition 335 (e.g., the messages will bedispatched according to the transmission rate and to the identifiedfulfillment center 390).

Examples 2 and 3 (below) include pseudocode for defining two exemplarydimension definitions 335 that are utilized to identify and routemessages 371 associated with new orders that should be prioritized.

EXAMPLE 2

{    ″duration″ : ″2 min″,    ″message_count″ : ″100″,    “priority” :HIGH;    ″process_type″ : ″OrderRequest″,    “partnerId” : “6559” }

EXAMPLE 3

{    ″duration″ : ″5 min″,    ″message_count″ : ″200″,    “is_anomalous”: true;    ″process_type″ : ″OrderRequest″,    “partnerId” : “6559” }

Each of these examples includes an additional parameter that is notincluded in Example 1. Specifically, the first dimension definition 335includes a “priority” parameter for identifying messages that are markedas high priority (e.g., because they require expedited shipping), andthe second dimension includes an “is_anomalous” parameter foridentifying messages 371 that should be prioritized because the metadatain the message indicates the presence of shipping exceptions (e.g.,indicates an order will be delivered late, an order was lost, an orderrequires a replacement, etc.). It should be noted that the transmissionrates in Examples 2 and 3 are higher than the transmission rate inExample 1 because the dimension definitions 335 in Examples 2 and 3 areutilized to expedite processing of messages that are deemed to behigh-priority. Messages 371 that have metadata matching the abovedimension definitions 335 can be transmitted via a dedicatedcommunication channel (e.g., to a dedicated computer, inbox, messagequeue, or individual) to expedite processing of the orders associatedwith the messages 371.

Examples 4 and 5 (below) include pseudocode for defining two exemplarydimension definitions 335 that are utilized to identify and routemessages 371 associated with order cancellations and inventory updates,respectively. This is accomplished by modifying the “process_type”parameter as shown below.

EXAMPLE 4

{    ″duration″ : ″15 min″,    ″message_count″ : ″500″,   ″process_type″ : ″OrderCancel″,    “partnerId” : “6559” }

EXAMPLE 5

{    ″duration″ : ″5 min″,    ″message_count″ : ″200″,    ″process_type″: ″Inventory″,    “partnerId” : “6559” }

It should be recognized that Examples 1-5 provided above are merelyintended to illustrate exemplary dimension definitions 335 that can beutilized to identify and route messages 371 received by themulti-dimensional event engine 330 to fulfillment centers 390. Theparameters can be modified accordingly to adjust the transmission rate,to identify other fulfillment centers 390, to identify other supplychains, and/or for other reasons. Additional parameters can be added tothe dimension definitions 335 as well (e.g., to include a facility typeparameter as described above and/or other types of parameters).

As evidenced by the disclosure herein, the principles set forth in thisdisclosure are rooted in computer technologies that overcome existingproblems in fulfillment systems, specifically problems dealing withproviding a highly available and redundant network topology for an eventengine that is configured to forward message events to fulfillmentsystems. The principles also are rooted in computer technologies thatovercome problems associated with effectively dispatching the messageevents to fulfillment centers. In known fulfillment systems, messagesare sent to fulfillment centers at static intervals (e.g., every halfhour), and those systems fail to provide proper redundancies to ensurethe system does not experience downtime. The principles described inthis disclosure provide a technical solution (e.g., one that utilizes anactive-standby network topology with a distributed locking mechanismthat can ensure high availability and redundancy, and one that enablesdynamic adjustment of transmission rates to fulfillment centers based ondetected network traffic) for overcoming such problems. Thistechnology-based solution marks an improvement over existing computingcapabilities and functionalities related to fulfillment systems byeliminating (or at least minimizing) system downtime and automaticallyadjusting transmission rates to fulfillment centers to allow for moreeffective and efficient processing of the messages. These systems aredesigned to improve the way fulfillment systems process orders, maintaininventories, and ensure continuous operations.

FIG. 4 is a sequence diagram 400 that illustrates how themulti-dimensional event engine 330 can automatically adjust transmissionrates for sending messages 371 (FIG. 3) to fulfillment centers 390. Anorder management system 370 transmits messages 371 (FIG. 3) to themulti-dimensional event engine 330. The messages 371 (FIG. 3) canpertain to requests for new orders, order cancellations, and/or ordermodifications that are submitted by customers (e.g., users 305 in FIG.3). The messages 371 (FIG. 3) also can pertain to inventory updates(e.g., which identify current levels of available inventory, scheduledinventory shipments to the fulfillment centers, or any other informationrelated to inventory).

The messages 371 (FIG. 3) can be transmitted to the multi-dimensionalevent engine 330 during times of peak traffic 410, medium traffic 420,or low traffic 430. The multi-dimensional event engine 330 is configuredto detect when the network (e.g., network 380 in FIG. 3) is experiencingpeak traffic 410, medium traffic 420, and low traffic 430. In certainembodiments, the determination of whether the network is experiencingpeak traffic 410, medium traffic 420, or low traffic 430 can be based onthe volume of messages 371 (FIG. 3) that are being received by the ordermanagement system 370 within a specified period of time. For example,the multi-dimensional event engine 330 can store threshold informationfor determining whether the volume of messages 371 (FIG. 3) constitutespeak traffic 410, medium traffic 420, or low traffic 430. Thedetermination of whether the network is experiencing peak traffic 410,medium traffic 420, or low traffic 430 can be made in other ways aswell.

The multi-dimensional event engine 330 transmits the messages 371 (FIG.3) to the appropriate fulfillment centers 390 according to anauto-adjusted transmission rate 440 that accounts for the level ofnetwork traffic. For example, messages 371 (FIG. 3) can be transmittedat a highest transmission rate during periods of peak traffic 410, alower transmission rate during periods of medium traffic 420, and alowest transmission rate during periods of low traffic 430. Transmittingthe messages 371 in this manner permits fulfillment centers 390 toprocess the messages more efficiently and to avoid late deliveries.

In certain embodiments, in order to modify the transmission rate, themulti-dimensional event engine 330 can adjust parameter settingsassociated with the dimension definitions (e.g., by adjusting theparameters for the time and batch size dimensions mentioned above).Alternatively, or additionally, the auto-adjusted transmission rate 440can be modified by selecting separate sets of dimension definitions 335(FIGS. 3 & 6) to be used during peak traffic 410, medium traffic 420,and low traffic 430. The separate sets of dimension definitions 335(FIGS. 3 & 6) can include varying settings for transmission rates basedon the varying levels of traffic.

Turning ahead in the drawings, FIG. 5 illustrates a flow chart for amethod 500 according to certain embodiments. Method 500 is merelyexemplary and is not limited to the embodiments presented herein. Method500 can be employed in many different embodiments or examples notspecifically depicted or described herein. In some embodiments, theactivities of method 500 can be performed in the order presented. Inother embodiments, the activities of method 500 can be performed in anysuitable order. In still other embodiments, one or more of theactivities of method 500 can be combined or skipped. In manyembodiments, system 300 (FIG. 3) can be suitable to perform method 500and/or one or more of the activities of method 500. In these or otherembodiments, one or more of the activities of method 500 can beimplemented as one or more computer instructions configured to run atone or more processing modules 601, 603, 605 (FIG. 6) of cloudenvironment 310 (FIGS. 3 & 6), order management system 370 (FIGS. 3, 4 &6), and fulfillment center 390 (FIGS. 3 & 6), respectively, andconfigured to be stored at one or more non-transitory memory storagemodules 602, 604, 606 (FIG. 6) of cloud environment 310 (FIGS. 3 & 6),order management system 370 (FIGS. 3, 4 & 6), and fulfillment center 390(FIGS. 3 & 6), respectively. The processing module(s) can be similar oridentical to the processing module(s) described above with respect tocomputer system 100 (FIG. 1).

Method 500 can comprise an activity 510 of detecting a current level ofnetwork traffic. As explained above, the multi-dimensional event engine330 can be configured to determine whether the network 380 (FIG. 3), thesystem 300 (FIG. 3), and/or the order management system 370 (FIGS. 3, 4,& 6) are currently experiencing peak traffic 410 (FIG. 4), mediumtraffic 420 (FIG. 4), or low traffic 430 (FIG. 4) levels. The networktraffic can be based, at least in part, on the volume or number ofmessages 371 (FIGS. 3 & 6) that are being received and/or transmitted byeither the order management system 370 (FIGS. 3, 4, & 6) and/or themulti-dimensional event engine 330 (FIGS. 3, 4, & 6).

Method 500 can further comprise an activity 520 of receiving messages371 (FIGS. 3 & 6) from an order management system 370 (FIGS. 3, 4, & 6).As explained above, the multi-dimensional event engine 330 (FIGS. 3, 4,& 6) can receive messages 371 (FIGS. 3 & 6) associated with customerrequests (e.g., requests to place new orders, cancel existing orders,and/or modify existing orders) and/or messages pertaining to inventory(e.g., messages that include updated inventory information). Themessages 371 (FIGS. 3 & 6) can be transmitted by the order managementsystem 370 (FIGS. 3, 4, & 6) and/or other system components.

Method 500 can further comprise an activity 530 of selecting atransmission rate for sending the messages 371 (FIGS. 3 & 6) to one ormore fulfillment centers 390 (FIGS. 3, 4, & 6) based on the currentlevel of network traffic that is detected. The transmission rate can bedefined utilizing the dimension definitions 335 (FIGS. 3 & 6) describedabove. Greater transmission rates are selected to handle greater levelsof network traffic, and lower transmission rates are utilized to handlelower levels of network traffic. The transmission rates can begranularly customized according to the specific traffic level that isdetected (e.g., using a function that granularly adjust the transmissionrate based on the specific traffic conditions currently detected) and/orcan be tiered to adjust the transmission rate when certain thresholdlevels of traffic are detected (e.g., incrementally adjusted whencertain threshold traffic levels are detected).

Method 500 can further comprise an activity 540 of transmitting themessages to the fulfillment centers in accordance with the transmissionrate that is selected. The messages can also be transmitted inaccordance with priority dimensions and/or supply chain dimensionsdescribed above. The messages can be transmitted via the network 380(FIG. 3) and/or directly to the fulfillment centers. The messages can bereceived by the fulfillment systems at the fulfillment centers.

Method 500 can further comprise an activity 550 of dynamically adjustingthe transmission rate in response to detecting changes in the networktraffic. As explained above, the multi-dimensional event engine 330(FIGS. 3, 4, & 6) transmits messages 371 (FIGS. 3 & 6) to the one ormore fulfillment centers 390 (FIGS. 3, 4, & 6) based on an auto-adjustedtransmission rate 440 (FIG. 4) that accounts for the network traffic. Incertain embodiments, the auto-adjusted transmission rate 440 (FIG. 4) isincreased in response to detecting an increased level of networktraffic, and is decreased in response to detecting a decreased level ofnetwork traffic. The messages are thereafter transmitted to thefulfillment centers in accordance with the adjusted transmission rate.

FIG. 6 illustrates a block diagram of a portion of system 300 comprisingthe cloud environment 310, multi-dimensional event engine 330, ordermanagement system 370, fulfillment center 390, and fulfillment system395 in FIG. 3 according to certain embodiments. Each of cloudenvironment 310, multi-dimensional event engine 330, order managementsystem 370, fulfillment center 390, and fulfillment system 395 is merelyexemplary and not limited to the embodiments presented herein. Each ofcloud environment 310, multi-dimensional event engine 330, ordermanagement system 370, fulfillment center 390, and fulfillment system395 can be employed in many different embodiments or examples notspecifically depicted or described herein. In some embodiments, certainelements or modules of cloud environment 310, multi-dimensional eventengine 330, order management system 370, fulfillment center 390, andfulfillment system 395 can perform various procedures, processes, and/oracts. In other embodiments, the procedures, processes, and/or acts canbe performed by other suitable elements or modules.

As explained above, the multi-dimensional event engine 330 can beimplemented using a topology 353 (FIG. 3) that is highly available andthat provides redundancy. For example, in certain embodiments, themulti-dimensional event engine 330 can be implemented in anactive-standby topology that includes an instance cluster 350 thatcomprises one or more active controller instances 351 (FIG. 3) and oneor more standby controller instances 352 (FIG. 3). A distributed lock610 is utilized to control which instance included in the instancecluster 350 is designated as an active controller instance 351 (FIG. 3).In response to the active controller instance 351 (FIG. 3) becomingunavailable, the distributed lock 610 is allocated to one of the standbycontroller instances 352 (FIG. 3), which thereafter becomes an activecontroller instance 351 (FIG. 3). This topology 353 (FIG. 3) minimizesdowntime of the multi-dimensional event engine 330.

The multi-dimensional event engine 330 stores dimension definitions 335.Each of the dimension definitions 335 can include one or more dimensionparameters 620. Exemplary dimension parameters 620 can include theparameters discussed above, which are utilized to specify transmissionrates (e.g., the time and batch size parameters), to identifyprioritized messages (e.g., the expedited shipping parameters and/oranomalous event parameters), and/or to enable customized flows forsupply chains and logistical measures (e.g., the message type, facilityidentifier, and facility type parameters).

The messages 371 received by the multi-dimensional event engine 330include metadata 640. The metadata 640 included in the messages 371 caninclude fields that correspond to one or more of the parameterdimensions 620 included in the dimension definitions 335. For example,the metadata 640 can include information that identifies whether themessage 371 is a high-priority message (e.g., because of expeditedshipping obligations and/or anomalous events). The metadata 640 canfurther include information that identifies the fulfillment center 390and/or the fulfillment system 395 that should receive the message 371.The metadata 640 can further include information that identifies themessage type (e.g., which indicates whether the message should beprocessed using a supply chain for new orders, order cancellations,inventory updates, etc.).

The multi-dimensional event engine 330 utilizes the dimension parameters620 and the metadata 640 to route messages 371 to appropriatefulfillment centers 390. The multi-dimensional event engine 330aggregates the messages into message batches 630 based on thiscomparison (e.g., based on the message type and based on the fulfillmentcenter) and periodically transmits the message batches 630 to thefulfillment centers 390. The message batches 630 are transmitted basedon the dimension parameters 620 specified in the dimension definitions335. As explained above, the multi-dimensional event engine 330 canautomatically adjust the transmission rates based on the level ofnetwork traffic.

Although systems and methods have been described with reference tospecific embodiments, it will be understood by those skilled in the artthat various changes can be made without departing from the spirit orscope of the disclosure. Accordingly, the disclosure of embodiments isintended to be illustrative of the scope of the disclosure and is notintended to be limiting. It is intended that the scope of the disclosureshall be limited only to the extent required by the appended claims. Forexample, to one of ordinary skill in the art, it will be readilyapparent that any element of FIGS. 1-6 can be modified, and that theforegoing discussion of certain of these embodiments does notnecessarily represent a complete description of all possibleembodiments. For example, one or more of the procedures, processes, oractivities of FIG. 5 can include different procedures, processes, and/oractivities and be performed by many different modules, in many differentorders.

All elements claimed in any particular claim are essential to theembodiment claimed in that particular claim. Consequently, replacementof one or more claimed elements constitutes reconstruction and notrepair. Additionally, benefits, other advantages, and solutions toproblems have been described with regard to specific embodiments. Thebenefits, advantages, solutions to problems, and any element or elementsthat may cause any benefit, advantage, or solution to occur or becomemore pronounced, however, are not to be construed as critical, required,or essential features or elements of any or all of the claims, unlesssuch benefits, advantages, solutions, or elements are stated in suchclaim.

Moreover, embodiments and limitations disclosed herein are not dedicatedto the public under the doctrine of dedication if the embodiments and/orlimitations: (1) are not expressly claimed in the claims; and (2) are,or potentially are, equivalents of express elements and/or limitationsin the claims under the doctrine of equivalents.

What is claimed is:
 1. A system comprising: one or more processingmodules; and one or more non-transitory storage modules storingcomputing instructions configured to run on the one or more processingmodules and perform acts of: initiating a cluster of controllerinstances in a cloud environment for executing a multi-dimensional eventengine that is configured to control routing of messages to one or morefulfillment centers; and configuring the cluster of controller instancesin a topology that provides availability and redundancy for themulti-dimensional event engine, wherein the topology applies adistributed lock to designate an active controller instance selectedfrom the cluster of controller instances to be utilized as themulti-dimensional event engine; wherein the active controller instanceselected to be utilized as the multi-dimensional event engine isconfigured to: detect a current level of network traffic; receive themessages from an order management system; select a transmission rate forsending the messages to the one or more fulfillment centers based on thecurrent level of the network traffic that is detected; transmit themessages to the one or more fulfillment centers in accordance with thetransmission rate; dynamically adjust the transmission rate to create anadjusted transmission rate in response to detecting changes in thenetwork traffic; and transmit additional ones of the messages to the oneor more fulfillment centers in accordance with the adjusted transmissionrate.
 2. The system of claim 1, wherein: the multi-dimensional eventengine stores dimension definitions that include a set of basedimensions for determining the transmission rate; the set of basedimensions comprises: a time parameter identifying a time period; and abatch size parameter identifying a threshold number of messages; and theactive controller instance for the multi-dimensional event engineaggregates the messages and transmits a batch of the messages to the oneor more fulfillment centers in response to the time period expiring orin response to the threshold number of messages being exceeded.
 3. Thesystem of claim 2, wherein dynamically adjusting the transmission rateincludes modifying the time period and the threshold number of messagesto adjust a frequency at which the batch of the messages is transmittedto the one or more fulfillment centers.
 4. The system of claim 3,wherein the active controller instance selected to be utilized as themulti-dimensional event engine is further configured to monitor thecurrent level of network traffic; and dynamically adjusting thetransmission rate comprises: automatically increasing the transmissionrate in response to detecting an increasing level of the networktraffic; and automatically decreasing the transmission rate in responseto detecting a decreasing level of the network traffic.
 5. The system ofclaim 1, wherein: the active controller instance of themulti-dimensional event engine stores dimension definitions that areconfigured to detect prioritized ones of the messages, including: firstprioritized ones of the messages associated with orders that requireprioritized shipping; and first prioritized ones of the messagesassociated with anomalous orders or shipping exceptions; and each of theprioritized ones of the messages is transmitted to the one or morefulfillment centers on a dedicated communication channel to expediteprocessing of the prioritized ones of the messages
 6. The system ofclaim 1, wherein: the multi-dimensional event engine stores dimensiondefinitions that include logistics information for identifying supplychains and designated fulfillment centers of the one or more fulfillmentcenters associated with the messages; and the logistics information isutilized by the multi-dimensional event engine to aggregate and routethe messages to the one or more fulfillment centers.
 7. The system ofclaim 1, wherein the active controller instance selected to be utilizedas the multi-dimensional event engine is further configured to: comparemetadata included in the messages received from the order managementsystem to dimension definitions stored by the multi-dimensional eventengine; aggregate the messages into groupings according the dimensiondefinitions; and transmit batches of the messages to the one or morefulfillment centers based on the groupings.
 8. The system of claim 1,wherein: controller instances of the cluster of controller instancesthat are not designated to be the active controller instance areselected to be utilized as standby controller instances; the standbycontroller instances are continuously polling a distributed lock manageto check an availability of the distributed lock; and in response to theactive controller instance becoming unavailable, one of the standbycontroller instances is selected to be utilized as the active controllerinstance using the distributed lock.
 9. The system of claim 8, whereinthe topology is an active-standby topology.
 10. The system of claim 1,wherein the messages received from the order management system comprise:messages associated with order requests; messages associated with ordercancellations; and messages associated with inventory updates.
 11. Amethod comprising: initiating, with one or more processing modules, acluster of controller instances in a cloud environment for executing amulti-dimensional event engine that is configured to control routing ofmessages to one or more fulfillment centers; and configuring, with theone or more processing modules, the cluster of controller instances in atopology that provides availability and redundancy for themulti-dimensional event engine, wherein the topology applies adistributed lock to designate an active controller instance selectedfrom the cluster of controller instances to be utilized as themulti-dimensional event engine; wherein the active controller instanceselected to be utilized as the multi-dimensional event engine isconfigured to: detect a current level of network traffic; receive themessages from an order management system; select a transmission rate forsending the messages to the one or more fulfillment centers based on thecurrent level of the network traffic that is detected; transmit themessages to the one or more fulfillment centers in accordance with thetransmission rate; dynamically adjust the transmission rate to create anadjusted transmission rate in response to detecting changes in thenetwork traffic; and transmit additional ones of the messages to the oneor more fulfillment centers in accordance with the adjusted transmissionrate.
 12. The method of claim 11, wherein: the multi-dimensional eventengine stores dimension definitions that include a set of basedimensions for determining the transmission rate; the set of basedimensions comprises: a time parameter identifying a time period; and abatch size parameter identifying a threshold number of messages; and theactive controller instance for the multi-dimensional event engineaggregates the messages and transmits a batch of the messages to the oneor more fulfillment centers in response to the time period expiring orin response to the threshold number of messages being exceeded.
 13. Themethod of claim 12, wherein dynamically adjusting the transmission rateincludes modifying the time period and the threshold number of messagesto adjust a frequency at which the batch of the messages is transmittedto the one or more fulfillment centers.
 14. The method of claim 13,wherein the active controller instance selected to be utilized as themulti-dimensional event engine is further configured to monitor thecurrent level of network traffic; and dynamically adjusting thetransmission rate comprises: automatically increasing the transmissionrate in response to detecting an increasing level of the networktraffic; and automatically decreasing the transmission rate in responseto detecting a decreasing level of the network traffic.
 15. The methodof claim 11, wherein: the active controller instance of themulti-dimensional event engine stores dimension definitions that areconfigured to detect prioritized ones of the messages, including: firstprioritized ones of the messages associated with orders that requireprioritized shipping; and first prioritized ones of the messagesassociated with anomalous orders or shipping exceptions; and each of theprioritized ones of the messages is transmitted to the one or morefulfillment centers on a dedicated communication channel to expediteprocessing of the prioritized ones of the messages.
 16. The method ofclaim 11, wherein: the multi-dimensional event engine stores dimensiondefinitions that include logistics information for identifying supplychains and designated fulfillment centers of the one or more fulfillmentcenters associated with the messages; and the logistics information isutilized by the multi-dimensional event engine to aggregate and routethe messages to the one or more fulfillment centers.
 17. The method ofclaim 11, wherein the active controller instance selected to be utilizedas the multi-dimensional event engine is further configured to: comparemetadata included in the messages received from the order managementsystem to dimension definitions stored by the multi-dimensional eventengine; aggregate the messages into groupings according the dimensiondefinitions; and transmit batches of the messages to the one or morefulfillment centers based on the groupings.
 18. The method of claim 11,wherein: controller instances of the cluster of controller instancesthat are not designated to be the active controller instance areselected to be utilized as standby controller instances; the standbycontroller instances are continuously polling a distributed lock manageto check an availability of the distributed lock; and in response to theactive controller instance becoming unavailable, one of the standbycontroller instances is selected to be utilized as the active controllerinstance using the distributed lock.
 19. The method of claim 18, whereinthe topology is an active-standby topology.
 20. The method of claim 11,wherein the messages received from the order management system comprise:messages associated with order requests; messages associated with ordercancellations; and messages associated with inventory updates.